home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
PROGRAM
/
TP030793.ARJ
/
03-07-93.TPC
Wrap
Text File
|
1993-03-07
|
32KB
|
937 lines
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-03-93 22:57:00
From Norbert Igl
To Dj Murdoch
Subject Functions Returning Strings
Hello Dj!
One of these days, Dj Murdoch wrote to Wilbert van Leijen:
DM> sp := StrPtr(Paramstr(1));
^^ hmmmmm.....
DM> Saved := 'Parameter one: '+sp^; { This fails, and messes up Sp^. }
typecasting a function...hmmmm
--- GoldEd 2.40p/FD2.02/FastEcho
* Origin: mother's finest. (:-) (2:2402/300.3)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:30:44
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-03-93 23:07:00
From Norbert Igl
To All
Subject Fast Fourier Transformation...
Hello All!
I'm searching for a quick FFT and inverse FFT ( in PAS or BASM )
for limiting the frequences in sound-samples.
Anyone ?
Norbert
--- GoldEd 2.40p/FD2.02/FastEcho
* Origin: May the source be with you... (2:2402/300.3)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:30:44
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-03-93 17:24:00
From Dj Murdoch
To Hans Siemons
Subject Re: source code included...
HS> The first thing is negotiable with the original author,
HS> the second thing is not. My license agreement states that
HS> I never release source with code from Borland's RTL in it.
That may in fact be negotiable. One of the packages I've released (TPFORT)
requires some code from the Object Professional library. I originally wrote
it to use compilation directives to switch between using OPro (so that owners
of OPro could recompile it) and including some code that I extracted from
OPro but didn't distribute. The latter meant that the compiled units didn't
Use OPro units, so anybody at all could link them into their programs, but
only I could recompile it in that form.
This eventually became too much trouble, and I contacted TurboPower Software.
They graciously allowed me to include the OPro extract with every copy that
I distributed, at no charge. I included a note thanking them, and it may
well be that this advertising has brought them extra business; I certainly
hope so.
I know that Borland is a much bigger company than TurboPower, so may be less
likely to be willing to respond to special requests like that. But it's worth
a try.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:30:45
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-01-93 16:56:00
From Dj Murdoch
To Chris Priede
Subject Re: .TPU and .OBJ files
CP> BTW, someone should write a program for disassembling TPUs to
TP
CP> 6.0+ compatible assembly source (BASM). While decompiling to Pascal
CP> source is practically impossible, this shouldn't be very difficult --
CP> tools like INTERFAC and TPU? already do most of the necessary work.
The
CP> output could then be compiled with other versions of TP. Anyone
looking
CP> for a project idea?
Unfortunately, BASM and .OBJ files can't call any routines from the System
unit, so to do this you'd need to provide alternates for all those routines
- possible, but really not very easy.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
--- RyPacker v2.5a
* Origin: RyBBS HomeBase `Home of RyBBS!' (414)-962-1098 (1:154/333)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:31:39
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-01-93 17:02:00
From Dj Murdoch
To Jason Duke
Subject Re: Editing big code... {$I}?
JD> Do most of you move segments of code that you never change
JD> to other files and then insert them with the {$I} command?
I almost never use $I. If something is needed in several places, I put it
in its own unit.
JD> Or do you just suffer the annoyance of hitting
JD> pageup/down twenty times every time you want to move from
JD> your CONSTANT definitions to the code you are working on?
JD> I am considering moving some parts of my code to other
JD> files for this reason... But I'm wondering what other programmers do.
?
Just open the same file twice in the IDE, and you can see two parts of it.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
--- RyPacker v2.5a
* Origin: RyBBS HomeBase `Home of RyBBS!' (414)-962-1098 (1:154/333)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:31:39
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-01-93 17:04:00
From Dj Murdoch
To Jason Duke
Subject Re: SIZES of variables, etc...
JD> I have a few questions. If I set something up to use
JD> constant A and it "recalls" this constant 20 times, is it
JD> faster than actually typing the constant in where it is
JD> needed?
It's just about identical in execution, but easier to maintain. Many
constants in programs should be named so that your program is easier to
modify later.
JD> Also, does the length of a variable name affect
JD> the size of the compiled file?
No. As long as you don't include debugging information with your program,
the name you use has no effect whatsoever on the program. (As long as you
don't step on another name, of course. :-)
JD> Is it faster to call a
JD> procedure 20 times or to type it in twenty times (I mean
JD> does it run any faster, not does it take longer to type it
JD> in)...
It's generally faster to have twenty copies of the procedure and avoid the
procedure call, but not always. Most machines these days have cached
memory, so if programs are small and stay in the cache, they'll run faster.
Of course, if you have to type the routine 20 times, it'll be a nightmare
to maintain. Use inline procedures instead.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
--- RyPacker v2.5a
* Origin: RyBBS HomeBase `Home of RyBBS!' (414)-962-1098 (1:154/333)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:31:40
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-01-93 17:13:00
From Dj Murdoch
To Travis Linton
Subject Re: documentation
TL> Is there anyone out there who has documentation for
TL> Borland Turbo Pascal 6 or 7 on disk. I'm too low on money
TL> at the moment to buy the book. Also does anyone know how
TL> to import TheDraw files into a prg and get them to show properly.
Thanks.
This sounds very much as though you have a pirated copy of TP/BP. I don't
really care if you do or not, but please don't post requests that sound
like attempted theft in this echo.
To others:
Please do not reply to posts like this, either positively or negatively.
If you want to give TL a lecture on the ethics of pirating software, DO IT
BY NETMAIL.
Duncan Murdoch
PASCAL Moderator
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
--- RyPacker v2.5a
* Origin: RyBBS HomeBase `Home of RyBBS!' (414)-962-1098 (1:154/333)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:31:40
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-01-93 18:30:00
From Dj Murdoch
To Benjamin Schollnick
Subject DLLs (was: rather foolish...)
BS> After 15-20 minutes of pouring over the manuals, I can't BS> find any
mention of that. I DON'T even see the DLL export
BS> ability. And I know that they did something there...
BS> (* Even thought that's only available via protected mode *)
Try Chapter 11 of the Language Guide, "Dynamic-Link Libraries".
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
--- RyPacker v2.5a
* Origin: RyBBS HomeBase `Home of RyBBS!' (414)-962-1098 (1:154/333)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:31:40
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-02-93 08:08:00
From Dj Murdoch
To Wilbert Van Leijen
Subject Re: Functions Returning Strings
DM> This isn't very safe programming.
WV> You're right - you should treat this pointer to a
WV> temporary string as a "constant" (read only) variable. TP
WV> has no provisions for this (yet) as far as function
WV> results are concerned. It's not that I want to put the
WV> blame on the language or its definition - it's simply an
WV> aspect I overlooked when I dreamt up this hack.
But it's not a constant - it's liable to change without any apparent action
by you. Try the example I sent:
sp := StrPtr(Paramstr(1));
Saved := 'Parameter one: '+sp^; { This fails, and messes up Sp^. }
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
--- RyPacker v2.5a
* Origin: RyBBS HomeBase `Home of RyBBS!' (414)-962-1098 (1:154/333)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:31:43
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 01-01-00 00:00:00
From
To
Subject
--- WM v2.07/92-0445
* Origin: The Storm Front BBS - (215)788-4339 v.32b (1:273/216)
* Tossed by SFToss/286 v1.02a on 93/03/05 09:32:37
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-03-93 21:39:00
From Dj Murdoch
To Benjamin Schollnick
Subject Re: DLLs (was: rather foolish...)
BS> (* Ah, just found it....Replace Unit with Library, and
BS> add 'export' to each procedure....They hid it *)
BS> But, what about *NON* protected mode app's?
BS> The DLL's only work with *PROTECTED* mode app's....I'm looking
BS> for a similiar ability for NON-Protected mode app's.
Borland doesn't offer one. I've been told that Topspeed Pascal has real mode
.DLLs, but I've never come across anyone who actually uses it.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:40
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-03-93 21:45:00
From Dj Murdoch
To Mitch Davis
Subject Re: tpu6->tpu7
MD> I'm just wondering if it would be possible to read
MD> in the old .TPU, add a sandwich to it, patch the places in
MD> the old .TPU where parts of the old system unit was called
MD> with the translator ruotines in the sandwich, and emit the
MD> new code in the form that the .TPUs of the newer version
MD> used. Just an idea.
I think there's no question that it would be possible to write an updater,
but it would be a lot of hard work. Last time I estimated it I guessed 200
hours, which probably really means 500. If you've got that much spare time
go for it.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:40
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-03-93 22:06:00
From Dj Murdoch
To Matt J. Metzinger
Subject Re: Source code MANGLER
MJ> I've been thinking about writing a source code
MJ> mangler. Can you _OR ANYONE_ give me an idea of all the
MJ> features that you would desire?
1. Strip comments. 2. Remove all unnecessary white space. 3. Convert
all possible identifiers to random names like I010I1, with as many re-uses
of the same identifier as possible.
Number 3 is the really hard one, because it means your program has to maintain
a symbol table to know what substitutions to make, and has to understand scoping
the same as the compiler so that it doesn't introduce errors when it recycles
a name, and has to know about interfaced identifiers so that it doesn't change
them.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:40
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-04-93 18:13:00
From Dj Murdoch
To Norbert Igl
Subject Re: Functions Returning Strings
DM> sp := StrPtr(Paramstr(1));
NI> ^^ hmmmmm.....
DM> Saved := 'Parameter one: '+sp^; { This fails, and messes up Sp^. }
NI> typecasting a function...hmmmm
No, I'm just evaluating a function. StrPtr is an inline function returning
a pointer to its argument. Here's Wilbert's declaration, from an earlier
message:
WV> Function StrPtr(Const s : String) : PString;
WV> InLine(
WV> $58/ { POP AX }
WV> $5A); { POP DX }
He presented this as an optimization; as my messages have said, it's not a
reliable one.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-04-93 18:26:00
From Dj Murdoch
To Norbert Igl
Subject Re: Fast Fourier Transformation...
NI> I'm searching for a quick FFT and inverse FFT ( in PAS or BASM )
NI> for limiting the frequences in sound-samples.
There's one in Numerical Recipes by Press et al; that's what I use. You can
find an old version of the code in NRPAS???.ZIP; it's available at garbo.uwasa.f
in /pc/turbopas, and probably on PDN nodes on Fidonet.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-04-93 18:50:00
From Dj Murdoch
To Hagen Lehmann
Subject Re: Making demos in TP 6.0
HL> > There is a bug in TP 6.0 (fixed in 7.0) that causes the
HL> Delay() procedure
HL> > to be inaccurate on some fast computers. I don't have accurate code to
HL> > fix it handy but someone in this echo should.
HL>
HL> Nono, it is not fixed in 7.0 because 7.0 uses the old System-routines.
HL>
HL> But here is a patch for 7.0:
I believe you're trying to help, but your post was very irresponsible, and
may cause damage to some people's systems.
1. I haven't heard of any Delay trouble in 7.0, and Borland has claimed that
the Delay bug is fixed.
2. TP/BP 7.0 certainly don't use the old System or CRT routines. There are
lots of changes in there, including the Delay code.
3. I'm not sure, but it looks to me as though your patch messes up something
in the AssignCRT routine.
In general, if you supply a patch, please provide both the bytes before and
after the change and describe what it does.
Duncan Murdoch
Moderator
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-04-93 18:55:00
From Dj Murdoch
To Steve Connet
Subject Re: julian dating
SC> Anyhow, here is the function ... please point out anything drastically
SC> wrong.
SC> FUNCTION JulianDate(Y : Word; M, D : Byte) : Word;
SC> CONST Start = 1993;
SC> Dm : Array [1..12] of Word =
SC> (31,59,90,120,151,181,212,243,273,304,334,365);
SC> BEGIN
SC> JulianDate := Dm[M-1]+D+(365*(Y-Start))+((Y-Start) Div 4)
SC> END;
You got the leap year correction wrong - it'll be wrong for all dates from
March 1, 1996 to Dec 31, 1996. You need to apply the leap day after Feb 28,
not at the end of the year.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-04-93 20:20:00
From Dj Murdoch
To Karen Pivazyan
Subject Re: SIZES of variables, etc...
KP> It doesn't matter if you use constants or actually type
KP> them in, since values are substituted for constant's names
KP> by preprocessor, before compiling.
Generally speaking, Pascal doesn't have a preprocessor. The compiler handles
constant declarations. Certainly that's true of Turbo Pascal.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-04-93 20:23:00
From Dj Murdoch
To Steve Connet
Subject Re: MOUSE
SC> writeln('MouseLib demo program, (c) 1992, Ron Loewy.');
I understand that you were trying to help, but please don't post code that
belongs to other people.
Duncan Murdoch
Moderator
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/06 11:37:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 19:28:00
From Dj Murdoch
To Aaron Marasco
Subject Re: TPU <-> BIN/OBJ
AM> Does anyone know of any way to convert a .TPU to a .BIN file to
AM> use BIN2OBJ.EXE and then load it as an external? Any help
AM> appreciated...
That wouldn't help. BIN2OBJ doesn't produce useful .OBJ files; it just sticks
binary data into a file with a fake entry point at the start.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:11:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 19:31:00
From Dj Murdoch
To Steve Connet
Subject Re: Date to LongInt
JR>SC> How do I convert a date string such as "19930227" to a LongInt? JR>SC>
The VAL command works only for Integers. Thank you.
JR>See the Lanquage Guide manual. It's on page p. 25 of
SC> the BP/TP7 Language JR>Guide, and in a similar location for previous
versions.
SC> Oh really? Then how come it doesn't work? Thanks for your reply.
You must be doing something wrong. It works for me:
var
l : longint;
error : integer;
s : string;
begin
val('19930227',l,error);
if error = 0 then
writeln(l);
end.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:11:41
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 07:52:00
From Dj Murdoch
To Bernie Pallek
Subject Re: BUFFERS
BP> To tell you the truth, I have never used New. I
BP> understand it's supposed to be OK, but I heard that GetMem
BP> is better, because you can de-allocate memory without
BP> having to use Mark and Release (or whatever those two are
BP> called). New doesn't look at the heap (I don't think it
BP> does, at least), and it just grabs a chunk of memory.
This is completely wrong. The two statements
New(p);
and
Getmem(p, sizeof(p^));
are *exactly* equivalent.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:12:52
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 08:14:00
From Dj Murdoch
To Bbs Writers
Subject Bugs in your software
The recent flood of messages from Greg Ryan's "ryBBS" shows a problem all too
common in this echo: software has bugs, and these bugs inconvenience all
of us.
This is a programmer's echo, so it's not surprising that a lot of different
software is used here, but developers should take special care to limit the
effect of their mistakes to their own system. Besides simple consideration
for others, think of the effect on your reputation of having your bugs spread
around the world.
Duncan Murdoch
Moderator
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:12:52
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 08:43:00
From Dj Murdoch
To All
Subject March 93 Guidelines for the PASCAL echo
First, a short summary of the rules:
o The topic is Pascal, in any form on any platform. Stay on topic!
o Try to make your messages be of interest to as many people as possible;
personal messages are always off-topic.
o Leave moderation to the moderator.
o NO FLAMING!
o If you post untested code, make that clear. It's better to test it first,
though.
o Religion, politics, copyright, and illegal activities are all off-topic.
o Try to work out your problem by yourself, first. If you can't get the
answer, then spend some time writing your question clearly.
o Try to give answers in as helpful a way as possible.
o All code posted should be public domain or specifically released for
non-profit use and distribution by the copyright holder.
o Keep origin lines less than 79 characters, tear lines less than 25
characters, and messages less than 16K in length.
o The moderator is DJ Murdoch, at 1:249/99.5.
o The full list of rules is posted monthly.
To all sysops:
Would all sysops please ensure that a copy of these guidelines is available
to all users of the PASCAL echo. I'd suggest cutting out the summary above
and having it print when users enter the PASCAL area of your BBS. You might
also make this a protected message to ensure that normal message area housekeepi
g does not not result in its being deleted. I try to re-post these guidelines
every month.
Duncan Murdoch
Pascal Moderator
GUIDELINES FOR THE PASCAL ECHO - THE DETAILS
The Pascal echo is an internationally distributed FidoNet echo devoted to
the discussion and promotion of the Pascal programming language in all its
variations.
MODERATOR.
The current moderator is Duncan Murdoch. I can be reached by Netmail at 1:249/99
5; by Compuserve mail to 71631,122; by Internet mail to dmurdoch@mast.queensu.ca
or by normal postage by writing to -
Duncan Murdoch
337 Willingdon Ave.
Kingston, Ontario, Canada
K7L 4J3
GUIDELINES.
1. Leave moderation to the moderator. Self appointed "echo policemen"
only waste echo space and create ill-feeling.
2. NO FLAMING. If you feel that you have been insulted in some way by
somebody, you have three options.
(a) Complain by netmail to the person concerned.
(b) Bring the matter to the moderator's notice - again by netmail.
(c) Ignore it. (the preferred option!)
3. Person-person messages that are not of general interest to other
users are STRICTLY not permitted. Netmail these types of messages.
4. When replying to messages try to do so "off-line" and quote some of
the message being replied to, but don't go overboard with quoting.
Quote just enough to enable the context of the reply to be fully
understood and in particular DO NOT INCLUDE PARTS OF THE TEAR AND
ORIGIN LINES.
Try reading over your reply before you commit yourself to sending
it. Try to anticipate the first question readers will ask, and add
the answer to your message.
5. When replying to questions with code examples, test them where
possible by compiling and running them (or state that you have not
done this). If possible always quote manual references, text
references etc.
6. If replying to a question where you are disagreeing with the other
person's code or statement/s, support your viewpoint with working
code examples or valid text references. This will be more productive
than unsupported statements. If you are not prepared to do this then
don't reply in the first place!
7. Do not ENTER or REPLY TO off-topic messages. The subject matter is
Pascal. Discussions on religion, politics, copyright, other
languages and personal messages are OFF-TOPIC. Any subject that is
illegal or undesirable in a responsible conference - eg discussion or
tips on producing viruses or how to illegally obtain access to
information that the user is unauthorised to obtain, is off-topic.
Sometimes messages from other conferences become linked into another
conference due to faulty software. Replying to, or commenting on, such
messages is off-topic.
The main point is to use common sense. Some light hearted banter can
relieve the formality and brighten up one's day but do not carry this to
the length where it becomes an extended thread. The object of the echo
is to help, get help and enjoy communicating with like-minded people.
8. No "thank-you" or "no content" or "rubbish" messages. Sysops spend a
great deal of time and money to enable the distribution of echoes
such as this. Please respect this and avoid messages such as "Thank
you. Just what I needed" or "I agree" etc. By observing this
etiquette you will be helping to ensure greater participation in the
future. If you miss a message or code for some reason, make your
own private arrangements to get it. Repeated postings of code are
expensive and unnecessary.
9. All messages are to be in the English language and must be in PLAIN
TEXT. No encryption of any kind is permissible. As the aim of the
conference is to help, discuss and demonstrate the Pascal language,
no .OBJ, .EXE or .COM files of any description are permitted
REGARDLESS of how they be constructed. The echo is NOT to be
regarded as a file transfer or exchange channel.
10. Limited, low key, on-topic advertising is permitted, provided that it
is authorised by the sysop of the originating BBS and by the
Moderator BEFORE it is posted here.
11. When seeking assistance -
a) If Turbo Pascal is your language, place the cursor on the key
word and call the on-line help (Ctrl-F1 in the IDE) to see if
the answer may be there.
b) Double check the manual to see if the answer is there.
c) When writing the message include enough code to allow would-be
helpers to have a chance to determine what the problem might be.
If possible condense the problem into a tiny working example and
post that.
d) This is a high volume echo so use a subject line in the message
that is likely to gain attention from the experts who are often
too busy to read every message. "Help wanted" or similar is a
good way to be ignored. Something like "Exec procedure not
working" is better.
e) Remember that a reply of "RTFM" is not considered or meant as an
insult. In fact it is considered a polite (in spite of the
connotations) way of reminding someone that the answer they seek
is in the manual.
f) Remember also that your reply may come from anyone, of possibly
unknown skill level. Don't be too upset if misled as it is
probably unintentional and will almost certainly be corrected by
another reader.
g) Many BBSs carry a file - FAQ.TXT (or similar) - which contains the
answers to frequently asked questions.
h) The PDN has a file TCSEL*.ARJ that contains many useful routines
that the previous moderator posted in the echo over the years. This
file also contains a file A2FAPQ.TXT which answers many commonly
asked questions.
12. When offering advice or help -
a) Do so in a helpful, polite manner. Don't be condescending - not
everybody may have your experience or skills.
b) Refer to the page in the manual where the answer is if your
answer is "RTFM"!
13. Messages should comply with the FidoNet message requirements. Origin
lines should not exceed 79 characters, tear lines must not exceed 25
characters and messages should not contain extended "internet" style
signatures. No encrypted text is permitted. Messages must be <16K.
14. All code posted should be public domain if possible. No copyrighted
code may be posted unless the copyright owner included permission for
non-profit reproduction and use in the original code. Code posted
without copyright claim will be regarded as in the Public Domain.
15. Election of Moderator. Under a normal situation, if the moderator
wishes to step aside, s/he will appoint a new moderator taking into
account the wishes of the regular users where possible. In the event
of a moderator ceasing to participate in the echo for a period of
three months without prior notice being given of the absence, for
whatever reason, then the ZEC (1:1/201) will conduct, or nominate a
regular and senior echo participant to conduct, an election for a new
moderator.
--- Msg V3.2
* Origin: Murdoch's_Point - - (1:249/99.5)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:12:53
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 19:40:00
From Norbert Igl
To J J Marquez
Subject Screen Print from PASCAL
Hello J!
One of these days, J J Marquez wrote to All'y'all:
JJM> How would I get a Turbo Pascal program to cause a screen print to
JJM> happen?
(:-)))) Inline( $cd/ $05 );
Norbert
--- GoldEd 2.40p/FD2.02/FastEcho
* Origin: mother's finest. (:-) (2:2402/300.3)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:12:56
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 23:34:00
From Norbert Igl
To Dj Murdoch
Subject Functions Returning Strings
Hello Dj!
One of these days, Dj Murdoch wrote to Norbert Igl:
DM>> sp := StrPtr(Paramstr(1));
NI>> ^^ hmmmmm.....
DM>> Saved := 'Parameter one: '+sp^; { This fails, and messes up Sp^. }
NI>> typecasting a function...hmmmm
DM> No, I'm just evaluating a function. StrPtr is an inline function returning
ahhh.. i missed that point.
DM> a pointer to its argument. Here's Wilbert's declaration, from an earlier
DM> message:
WV>> Function StrPtr(Const s : String) : PString;
WV>> InLine(
WV>> $58/ { POP AX }
WV>> $5A); { POP DX }
DM> He presented this as an optimization; as my messages have said, it's not a
DM> reliable one.
...even worse, "StrPtr" reads like a type's name , not a function.
Str2Ptr would have been better .... i would'nt have mixed it up !
Norbert
--- GoldEd 2.40p/FD2.02/FastEcho
* Origin: Fly like an Igl (2:2402/300.3)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:12:56
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Conference 4
Date 03-05-93 23:31:00
From Norbert Igl
To Dj Murdoch
Subject Fast Fourier Transformation...
Hello Dj!
One of these days, Dj Murdoch wrote to Norbert Igl:
NI>> I'm searching for a quick FFT and inverse FFT ( in PAS or BASM )
NI>> for limiting the frequences in sound-samples.
DM> There's one in Numerical Recipes by Press et al; that's what I use. You
DM> can find an old version of the code in NRPAS???.ZIP; it's available at
DM> garbo.uwasa.fi in /pc/turbopas, and probably on PDN nodes on Fidonet.
I found NRPAS13.* nearby... thanks !
Norbert
--- GoldEd 2.40p/FD2.02/FastEcho
* Origin: Fly like an Igl (2:2402/300.3)
* Tossed by SFToss/286 v1.02a on 93/03/07 02:12:57